Including Advanced Data Fields

Your source can also include Advanced Data Fields. Advanced data fields automate chart formatting and can be used to identify assistant boxes, insert sub-chart breaks, hide branches, or specify the chart styles of selected branches. In addition, advanced data fields can also be used to identify rows to ignore during the import process.

In order to use advanced data fields, you must include a header row in your import file. The header must with contain columns that correspond to each utilized advanced data field. If you are importing from a database, the fields in the source database table (or view) must be named to match an advanced data field. A typical Excel import file would be constructed as follows:

The following sections describe the available advanced data fields:

IsAssistant

If the IsAssistant field is included in an import file, OrgPlus can automatically format assistants in your chart. Setting IsAssistant to 1 for a record makes the corresponding box an assistant.

For example, if the IsAssistant field for Corinne Speer is set to 1 in the import file, the resulting chart is formatted as follows:

Note: You can specify an assistant branch style in the IsAssistant column (refer to the table in the BranchStyle section below).

BreakAt

If the BreakAt field is included in an import file, OrgPlus automatically inserts a sub-chart break for the corresponding record.

╖          Setting BreakAt to 0 does not insert a sub-chart break.

╖          Setting BreakAt to 1 inserts a sub-chart break.

╖          Setting BreakAt to a text string (such as, Marketing) inserts a sub-chart break and names the sub-chart based on the text.

CollapseAt

If the CollapseAt field is included in an import file, OrgPlus automatically collapses or expands the branch associated with each box. Setting CollapseAt to 1 collapses a branch.

BranchStyle

Using the BranchStyle field allows you to define the chart style for each branch in your chart. By default, charts created using the Import Wizard select chart styles that minimize the total number of pages and optimize the distribution of boxes on each page.

The following branch styles are available:

Sequence

The Sequence field allows you to control the order in which subordinate boxes are arranged under a manager. Boxes are sequenced from left to right and then top to bottom.

 For example, importing the following data à

à would create the following chart:

Notice that Larry Stevens, assigned sequence number 3, is third from the left.

The Sequence field can also be used to sequence subordinates in multiple rows and columns beneath a manager. To achieve this, enter row number and sequence number separated by a : for each import record.

For example, importing the following data à

à would create the following chart:

Exclude

The Exclude field allows you to determine how each box in your chart is handled with respect to calculations.

╖          Setting Exclude to 0 includes a box in all counts and calculations.

╖          Setting Exclude to 1 excludes a box from all counts and calculations.

╖          Setting Exclude to 2 excludes a box from all counts.

╖          Setting Exclude to 3 excludes a box from all calculations.

Format

The Format field allows you to specify the format for any given box. The example below contains a subset of available options. See the OrgPlus Knowledge Base at www.orgplus.com/support for more information on the Format advanced data field.

Special

The Special field allows you to specify chart formatting parameters such as chart title and chart background color. See the OrgPlus Knowledge Base at www.orgplus.com/support for more information on the Special field.

The Special field can also be used to ignore any row from the import data source. For example, as shown below, an Excel file containing a summary row.

AuxReportsTo

The AuxReportsTo field allows you to specify one or more auxiliary reporting relationship within your chart.

Importing the following data:

Would result in the following chart:

Note: Multiple auxiliary reporting relationships for a single record must be separated by semi-colons.